Referent system for devices of an nfv network

ABSTRACT

A network functions virtualization (NFV) network can be configured to operate according to NFV protocols that decouple software functionality from specific hardware elements. A referent system can be provided that identifies a precise physical location of devices associated with the NFV network relative to other equipment or devices associated with the NFV network.

RELATED APPLICATION

The present application is a continuation of, and claims priority toeach of: U.S. patent application Ser. No. 15/859,941 (now U.S. Pat. No.9,887,882), filed Jan. 2, 2018, and entitled “A REFERENT SYSTEM FORDEVICES OF AN NFV NETWORK,” which is a continuation of U.S. patentapplication Ser. No. 14/737,867, filed Jun. 12, 2015, and entitled “AREFERENT SYSTEM FOR DEVICES OF AN NFV NETWORK”. The entireties of theseapplications are hereby incorporated by reference herein.

TECHNICAL FIELD

The present application relates generally to associating a networkfunctions virtualization (NFV) function created in a virtual environmentwith a referent system that identifies a precise physical location ofthe device that is executing the NFV function and/or providing thevirtual environment.

BACKGROUND

In the domain of network architecture, there is an ongoing researchtrend, both in industry and academia, directed toward exploring thepossibility of implementing software-defined networking (SDN) andnetwork functions virtualization (NFV) for at least a portion of anetwork. Primary motivations for such a transition are a reduction ofthe custom hardware costs and performance enhancements.

BRIEF DESCRIPTION OF THE DRAWINGS

Numerous aspects, embodiments, objects and advantages of the presentinvention will be apparent upon consideration of the following detaileddescription, taken in conjunction with the accompanying drawings, inwhich like reference characters refer to like parts throughout, and inwhich:

FIG. 1 illustrates a block diagram of an example system that can providefor a referent system indicative of a geographical or physical locationof devices associated with an NFV Network in accordance with certainembodiments of this disclosure;

FIG. 2 provides an illustration that depicts various examples of theother equipment in accordance with certain embodiments of thisdisclosure;

FIG. 3 illustrates a graphical depiction of an example referent systemthat hierarchically identifies the network device in relation to theother equipment specified by the referent system in accordance withcertain embodiments of this disclosure;

FIG. 4 illustrates a table that depicts various examples of the referentidentifier data in accordance with certain embodiments of thisdisclosure;

FIG. 5 illustrates a block diagram of an example system that thatprovides for a network health monitoring device that can leverage thereferent system to identify a physical location of the network device inaccordance with certain embodiments of this disclosure;

FIG. 6 illustrates a block diagram of an example system that illustratesthe network health monitoring device monitoring a group of devicesassociated with the NFV network and transmitting various indicators inresponse to status data in accordance with certain embodiments of thisdisclosure;

FIG. 7 illustrates an example methodology that can provide for areferent system indicative of a geographical or physical location ofdevices associated with an NFV Network in accordance with certainembodiments of this disclosure; and

FIG. 8 illustrates an example methodology that can provide foradditional features or aspects in connection with providing a referentsystem for elements of the NFV Network in accordance with certainembodiments of this disclosure.

DETAILED DESCRIPTION Overview

Network functions virtualization (NFV) can be employed to virtualizecomponents (e.g., nodes, switches, interfaces, etc.) of a network,wherein virtual machines located in a cloud or virtual environment canperform processing that was previously performed by custom hardwaredevices these virtualized components replace in an NFV architecture.These virtual machines can be readily instantiated or destroyed in thecloud with very little effort and represent a separation of hardwarefrom software. In other words, NFV can be implemented in connection withcloud-based computing instead of requiring localized custom hardware toperform the same functions—hence, the network functions being executedare no longer tied to custom hardware.

As noted, there are advantages to implementing a network according toNFV architecture. For example, since NFV represents a separation betweenhardware and software, virtual environments can be constructed byservers or other devices that are physically located substantiallyanywhere in the world instead of being tied to a specific location, asis the case with previous network architectures. For instance,traditional hardware tasked with providing a service to network userswas generally tied to a physical location associated with that serviceor a related network element. In contrast, this same service can beprovided by leveraging a virtual environment that is constructed bydevices that are not tied to any specific physical location. Moreover,the devices can be commodity-based servers rather thanapplication-specific custom devices and hence less expensive to operateand maintain.

However, separating hardware from software in connection with networkfunctions, which represents an advantage that is provided by NFV, alsointroduces challenges that are not present for many other types ofnetworks. In this regard, generally due to the fact that NFV operates toseparate hardware and software elements, identifying the locationassociated with a specific device represents a distinct challenge.

The disclosed subject matter relates to a referent system that can beutilized to identify a precise physical location of devices associatedwith NFV networks. Such can be advantageous for a number of reasons. Forexample, consider the case in which a network device of a traditionalnetwork fails. Typically, such was remedied by dispatching servicepersonnel to repair or replace the failing network device, which oftenrepresented a significant expense and possibly interrupted service for asignificant amount of time. Historically, however, due to the tightcoupling between hardware and software elements of traditional networks,these service personnel generally knew which failing network devicerequired service and knew the location of that device.

Now consider a similar example in which a network device thatinstantiates a network function in a virtual environment associated withan NFV network. Suppose an error of some type occurs and the networkfunction does not execute as intended. One of the advantages of an NFVnetwork is that the network function can be moved and/or re-instantiatedand executed by other devices of the network, generally without anyinterruption to the service and at virtually no cost. However, if theerror occurred due to hardware failure or the like, service personnelgenerally do not have a good idea which physical device is failing andneeds service, largely because there is no tight coupling betweenhardware and software elements, as is the case for traditional networks.

A given building might have many floors, each with many aisles ofcomputing devices that operate in connection with the network. Each ofthese aisles might have many device bays, and each of the device bayscan have multiple shelves, and within each shelf, multiple devices thatcan execute the network function. Such can be a difficult undertaking toidentify which device, from among potentially many thousands, requiresservice. Such a difficulty can be further compounded by the fact thatmany such buildings might exist, distributed at various locationsthroughout the world.

Another advantage provided by the disclosed referent system can relateto selecting devices at specific locations for instantiating networkfunctions. Consider a network service that critically requires lowlatency between various interoperating network functions. As anotherexample, consider a network service that has very stringent regulatorydemands relating to that service or the underlying equipment. In theseand other cases, the referent system can be used to select specificdevices that are used to execute a particular network function. Forexample, devices in very close geographic proximity can be selected toexecute interoperating network functions that have low latencyconstraints or devices at a very specific location can be specificallyselected to execute network functions in order to accommodate regulatoryor other constraints.

NFV Referent System Architectures

The disclosed subject matter is now described with reference to thedrawings, wherein like reference numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the disclosed subject matter. It may beevident, however, that the disclosed subject matter may be practicedwithout these specific details. In other instances, well-knownstructures and devices are shown in block diagram form in order tofacilitate describing the disclosed subject matter.

Referring now to the drawing, with reference initially to FIG. 1,network device 100 is depicted. Network device 100 can provide for areferent system (e.g., referent system 108) indicative of a geographicalor physical location of devices associated with an NFV Network 101. Insome embodiments, the referent system can be associated with a networkfunction so that a precise physical location of the device executing thenetwork function can be determined. In some embodiments, the referentsystem can be leveraged to select a device to be used to execute anetwork function, for instance selecting a precise physical locationthat is to be the location of devices executing the network function.Generally, network device 100 can comprise a processor and a memory thatstores executable instructions that, when executed by the processor,facilitate performance of operations. Said processor and memory, as wellas other suitable computer or computing-based elements, can be used inconnection with implementing one or more of the systems or componentsshown and described in connection with FIG. 1 and other figuresdisclosed herein.

Network device 100 can be configured to execute network function 102according to one or more NFV protocol(s) 103. For example, NFVprotocol(s) 103 can define rules relating to functions of a NFV network101 being provided in virtual environment 104. In some embodiments,virtual environment 104 can be generated by network device 100 or bymany network devices, including network device 100, associated with theNFV network.

In some embodiments, network device 100 can associate network function102 with referent identifier data 106, which can be identifier datadefined by referent system 108. Referent identifier data 106 cancomprise device data 110 and reference data 112.

Device data 110 can specifically identify network device 100. Hence,device data 110 can be used to identify the device (e.g., network device100) that is executing network function 102. Additionally oralternatively, device data 110 can be used to select a specific device(e.g., network device 100) to execute or instantiate network function102. In some embodiments, device data 110 identifies network device 100relative to other equipment 114 associated with the NFV Network 101,which provides certain advantages over other identification techniquessuch as utilizing media access control (MAC) address data or the like,as further detailed herein. As used herein, other equipment 114 iscontemplated to include any suitable equipment related to the NFVnetwork 101 other than network device 100, which can be identifiedrelative to the other equipment 114.

Reference data 112 can represent data that identifies the otherequipment 114. In some embodiments, referent identifier data 106 canindicate a physical location of network device 100 and the otherequipment 114. FIG. 2 illustrates various examples of other equipment114, FIG. 3 depicts an example of a hierarchical referent system 108 inconnection with other equipment 114, and FIG. 4 depicts an example ofreferent identifier data 106 that is defined by referent system 108, allof which are intended to be referenced in conjunction with FIG. 1.

Turning now to FIG. 2, illustration 200 is provided. Illustration 200depicts various examples of the other equipment 114. For instance, otherequipment 114 can relate to building structure 202 or a floor structure204. In those cases, the associated referent identifier data 106 canidentify the particular building structure 202 as well as identify aspecific floor of the building associated with floor structure 204 thatgenerally includes devices associated with NFV network 101. Additionallyor alternatively, other equipment 114 can comprise an aisle structure206 that can comprise a group of devices associated with the NFV Network101, a bay structure 208 that can comprise a group of devices associatedwith the NFV Network 101, a shelf structure 210 that can comprise agroup of devices associated with the NFV Network 101, or any othersuitable structure or device. It is understood that other equipment 114can represent substantially any equipment associated with the NFVNetwork 101 or any structure or housing that comprises devices such asnetwork device 100 that execute network functions of an NFV Network 101.Hence, the examples provided herein are referred to by convention, butother conventions or terminology is contemplated and, where suitable, isconsistent with the disclosed referent system 108 and/or other disclosedsubject matter.

FIG. 3 provides a graphical depiction 300 of an example referent system108 that hierarchically identifies network device 100 in relation to theother equipment 114 specified by the referent system 108. At the upperhierarchical levels, a country or region 302 can be identified, as wellas a city 304 within that country or region 302. Below these are themiddle hierarchical levels, building structure 202 and floor structure204. Hence, referent system 108 is contemplated to identify a particularfloor of a particular building that is in a particular city of aparticular country.

At the lowest hierarchical level in this example, is device 100 thatexecutes network function 102. This device might be located within aspecific shelf structure 210 that is in a specific bay structure 208, ofa specific aisle structure 206 that is on the floor of the buildingindicated above.

It is understood that the upper hierarchical levels (e.g., 302, 304,etc.) and in some cases the middle levels associated with structures 202and/or 204 can be identified by other referent systems and/or otherlocation-based services such as global position satellite (GPS) or othertrilateration or multi-lateration techniques. Hence, the disclosedsubject matter can be used in combination with other referent systems,generally to identify the higher hierarchical tiers. It is appreciated,however, that the disclosed referent system 108 can describe a locationof a specific device with much greater granularity than can be providedby other location-based services. One of the innovative aspects of thedisclosed referent system 108 is that this precise location can bespecified and/or identified relative to other equipment 114 associatedwith the NFV Network 101, which makes effective use of hierarchy such asthat provided in graphical depiction 300.

With reference now to FIG. 4, illustration 400 is provided. Illustration400 depicts various examples of the referent identifier data 106. Asdetailed previously, referent identifier data 106 can include referencedata 112 that is indicative of other equipment 114 and device data 110that identifies network device 100 relative to the other equipment 114.

In this example, reference data 112 includes four columns of data,indicated as “Location”, “Aisle”, “Bay”, and “Shelf”. It is assumed thatdata associated with the “Location” column sufficiently represents alocation in the context of a specific country, region, city, building,floor, or other pertinent data. Such data can be provided by a differentreferent system (e.g., GPS) and transformed to the example referentsystem 108 depicted here. The subsequent columns, “Aisle”, “Bay”, and“Shelf” can expressly represent other equipment 114, and specificallyelements 206, 208, and 210, respectively. It is understood thatindividual identifiers for these columns can, like device data 110, bean identifier that is relative to other (e.g., higher hierarchical tier)equipment 114.

In some embodiments, and due to the hierarchical nature of examplereferent system 108, device data 110 can be a non-unique identifierwithin referent system 108. Such is illustrated by boxes 402 a and 402b, which both depict the same identifier for two different networkdevices. Similarly, reference data 112 can be a non-unique identifierfor certain other equipment 114, as illustrated by box 404, which bothdescribe in this example the same shelf structure 210, even thoughreferring to different devices within that shelf structure 210. However,referent identifier data 106, which represents a combination of(potentially non-unique) reference data 112 and (potentially non-unique)device data 110 can be unique within referent system 108, as illustratedby box 406. Hence, a precise location of a network device (e.g., networkdevice 100) that does execute or is available to execute a networkfunction (e.g., network function 102) at a particular time can beidentified by referent system 108.

Turning back FIG. 1, in some embodiments, network device 100 candetermine move data 116. Move data 116 can relate to a move associatedwith network function 102. In some embodiments, this move (which can becharacterized and/or facilitated by move data 116) of network function102 can relate to transferring execution of network function 102 fromnetwork device 100 to another network device (not shown) of the NFVnetwork 101. For example, network device 100 can terminate processesrelated to the execution of network function 102 and the other devicecan instantiate processes related to the execution of network function102. It is understood that when network device 100 off-loads thecomputing/processing of network function 102 to the other device, thephysical location of the computing elements that are executing networkfunction 102 has likely changed. Referent identifier data 106 can beupdated to reflect this change. Additionally or alternatively, referentsystem 108 can be accessed in order to specify or select a suitablephysical location or area where network function 102 is to be off-loadedor instantiated, and the execution of network function 102 can be movedto one or more devices at that location or area, as described byreferent system 108.

In some embodiments, move data 116 associated with a move of networkfunction 102 can relate to a change in a physical location associatedwith network device 100. For example, consider a mobile computingplatform that collects data relating to weather events that is moved toavoid adverse weather such as a tornado or hurricane. It is appreciatedthat although the physical device executing network function 102 (e.g.,network device 100) has not changed, the actual physical location ofthat device has changed as a result of the move and these changes can bereflected by an appropriate update to referent identifier data 106and/or selected or determined in advance of the move based on referentsystem 108 (e.g., to select where to move the network device).

It is understood that there are many reasons why network function 102might be moved or why identifying in advance of a move a desirabletarget (e.g., device or location) for the move. For example, certainnetwork functions might be subject to legal, regulatory, or contractualobligations to be executed within specified geographic boundaries or tobe executed at certain local times (e.g., “follow the sun”). As anotherexample, disaster recovery (e.g., weather, political, etc.) events mightlead to a move as might capacity management issues, performancemanagement issues, or equipment failure events.

Regardless of the reasons, moving a network function 102 createsdifficulties for other reference systems. For example, relying on MACaddresses or the like might provide an ID for the device executing anetwork function, but says nothing specific as to the actual physicallocation of that device, particularly after a move. GPS or otherlocation-based services can provide a physical location reference, butrequire additional equipment for devices and often do not providelocation information to the resolution of what might be required formany applications since identifying a city or even a particular buildingor floor can still be insufficient to readily locate a given networkdevice in many instances. Advantageously, the disclosed referent system108 can mitigate certain deficiencies of other reference systems and canprovide for updating appropriate information in response to changes inthe physical location of the device(s) executing network function 102.

Referring now to FIG. 5, system 500 is illustrated. System 500 providesfor a network health monitoring device 502 that can leverage thereferent system 108 to identify a physical location of the networkdevice 100. In some embodiments, network health monitoring device 502can receive status data 504 from network device 100 or from anotherdevice or equipment associated with the NFV Network 101. Receipt ofstatus data 504 can be in accordance with push or pull techniques orbased on a schedule. Put differently, network device 100 can initiatetransmission of status data 504, transmit status data 504 in response toa request (e.g., from network health monitoring device 502), or inaccordance with a schedule.

Status data 504 can include referent identifier data 106 as detailedherein. Furthermore, status data 504 can include various status-baseddata such as, for example, spare capacity message 506 that indicatesnetwork device 100 has spare computing capacity, maintenance message 508that indicates network device 100 requires maintenance, or some othersuitable indication of a state or status associated with network device100. In response to status data 504, network health monitoring device502 can determine location data 510 indicative of a physical location ofnetwork device 100 based on the referent identifier data 106 included instatus data 504.

Turning now to FIG. 6, system 600 is illustrated. System 600 illustratesthe network health monitoring device 502 monitoring a group of devicesassociated with the NFV network 101 and transmitting various indicatorsin response to status data. In this example, network devices 602 canrepresent a group of all or a portion of the devices that provide NFVnetwork 101. The devices of the group of network devices 602 can besubstantially similar to network device 100, as described herein, and/orthe group of network devices 602 can include network device 100.Likewise, status data 604 represent a group of individual statusindicators from all or a portion of the individual network devices 602,any of which can be substantially similar to status data 506 detailedherein. For example, status data 602 can include referent identifier 106for the associated network device 602 and an associated statusindicator.

In response to receiving status data 604, network health monitoringdevice 502 can transmit location data 510 associated with the particularnetwork device(s) 602 and an appropriate status indicator (e.g., 506,508, etc.) to other network elements or devices that can facilitateappropriate action in response.

Methods for NFV Architecture Referent System

FIGS. 7 and 8 illustrate various methodologies in accordance with thedisclosed subject matter. While, for purposes of simplicity ofexplanation, the methodologies are shown and described as a series ofacts, it is to be understood and appreciated that the disclosed subjectmatter is not limited by the order of acts, as some acts may occur indifferent orders and/or concurrently with other acts from that shown anddescribed herein. For example, those skilled in the art will understandand appreciate that a methodology could alternatively be represented asa series of interrelated states or events, such as in a state diagram.Moreover, not all illustrated acts may be required to implement amethodology in accordance with the disclosed subject matter.Additionally, it should be further appreciated that the methodologiesdisclosed hereinafter and throughout this specification are capable ofbeing stored on an article of manufacture to facilitate transporting andtransferring such methodologies to computers.

Turning now to FIG. 7, exemplary method 700 is depicted. Method 700 canprovide for a referent system indicative of a geographical or physicallocation of devices associated with an NFV Network. For example, atreference numeral 702, a network function can be executed according to anetwork functions virtualization protocol that defines rules relating tofunctions of a network being provided in a virtual environmentconstructed by the device.

At reference numeral 704, a first portion of referent identifier dataassociated with a referent system can be received. The first portion cancomprises reference data that identifies other equipment of the network.At reference numeral 706, a second portion of the referent identifierdata can be received. The second portion can comprise device data thatidentifies the device relative to the other equipment.

At reference numeral 708, the network function can be associated withreferent identifier data. Hence, the network function is associated withdata that identifies the device that is executing the network function.Such data can, for example, indicate a precise physical location of thedevice that is executing the network function. Method 700 can proceed toinsert A, which is further detailed in connection with FIG. 8, or end.

With reference now to FIG. 8, exemplary method 800 is illustrated.Method 800 can provide for additional features or aspects in connectionwith providing for a referent system for elements of an NFV Network. Forexample, at reference numeral 802, transmission of status data can befacilitated. The status data can be transmitted to a monitoring devicein response to a determination that the device has spare computingcapacity, wherein the status data comprises the referent identifier dataassociated with the device and indicates the device has spare computingcapacity.

At reference numeral 804, transmission of status data can befacilitated. In this example, the status data can be transmitted to amonitoring device in response to a determination that the devicerequires service, wherein the status data comprises the referentidentifier data associated with the device and indicates the devicerequires service.

As used in this application, the terms “system,” “component,”“interface,” and the like are generally intended to refer to acomputer-related entity or an entity related to an operational machinewith one or more specific functionalities. The entities disclosed hereincan be either hardware, a combination of hardware and software,software, or software in execution. For example, a component may be, butis not limited to being, a process running on a processor, a processor,an object, an executable, a thread of execution, a program, and/or acomputer. By way of illustration, both an application running on aserver and the server can be a component. One or more components mayreside within a process and/or thread of execution and a component maybe localized on one computer and/or distributed between two or morecomputers. These components also can execute from various computerreadable storage media having various data structures stored thereon.The components may communicate via local and/or remote processes such asin accordance with a signal having one or more data packets (e.g., datafrom one component interacting with another component in a local system,distributed system, and/or across a network such as the Internet withother systems via the signal). As another example, a component can be anapparatus with specific functionality provided by mechanical partsoperated by electric or electronic circuitry that is operated bysoftware or firmware application(s) executed by a processor, wherein theprocessor can be internal or external to the apparatus and executes atleast a part of the software or firmware application. As yet anotherexample, a component can be an apparatus that provides specificfunctionality through electronic components without mechanical parts,the electronic components can comprise a processor therein to executesoftware or firmware that confers at least in part the functionality ofthe electronic components. An interface can comprise input/output (I/O)components as well as associated processor, application, and/or APIcomponents.

Furthermore, the disclosed subject matter may be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques to produce software, firmware, hardware,or any combination thereof to control a computer to implement thedisclosed subject matter. The term “article of manufacture” as usedherein is intended to encompass a computer program accessible from or bya computing device.

As is employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor also can be implemented as acombination of computing processing units.

In the subject specification, terms such as “store,” “data store,” “datastorage,” “database,” “repository,” “queue”, and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can comprise both volatile andnonvolatile memory. In addition, memory components or memory elementscan be removable or stationary. Moreover, memory can be internal orexternal to a device or component, or removable or stationary. Memorycan comprise various types of media that are readable by a computer,such as hard-disk drives, zip drives, magnetic cassettes, flash memorycards or other types of memory cards, cartridges, or the like.

By way of illustration, and not limitation, nonvolatile memory cancomprise read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable ROM (EEPROM), or flashmemory. Volatile memory can comprise random access memory (RAM), whichacts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), anddirect Rambus RAM (DRRAM). Additionally, the disclosed memory componentsof systems or methods herein are intended to comprise, without beinglimited to comprising, these and any other suitable types of memory.

In particular and in regard to the various functions performed by theabove described components, devices, circuits, systems and the like, theterms (including a reference to a “means”) used to describe suchcomponents are intended to correspond, unless otherwise indicated, toany component which performs the specified function of the describedcomponent (e.g., a functional equivalent), even though not structurallyequivalent to the disclosed structure, which performs the function inthe herein illustrated exemplary aspects of the embodiments. In thisregard, it will also be recognized that the embodiments comprises asystem as well as a computer-readable medium having computer-executableinstructions for performing the acts and/or events of the variousmethods.

Computing devices typically comprise a variety of media, which cancomprise computer-readable storage media and/or communications media,which two terms are used herein differently from one another as follows.Computer-readable storage media can be any available storage media thatcan be accessed by the computer and comprises both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media cancomprise, but are not limited to, RAM, ROM, EEPROM, flash memory orother memory technology, CD-ROM, digital versatile disk (DVD) or otheroptical disk storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or other tangible and/ornon-transitory media which can be used to store desired information.Computer-readable storage media can be accessed by one or more local orremote computing devices, e.g., via access requests, queries or otherdata retrieval protocols, for a variety of operations with respect tothe information stored by the medium.

On the other hand, communications media typically embodycomputer-readable instructions, data structures, program modules orother structured or unstructured data in a data signal such as amodulated data signal, e.g., a carrier wave or other transportmechanism, and comprises any information delivery or transport media.The term “modulated data signal” or signals refers to a signal that hasone or more of its characteristics set or changed in such a manner as toencode information in one or more signals. By way of example, and notlimitation, communications media comprise wired media, such as a wirednetwork or direct-wired connection, and wireless media such as acoustic,RF, infrared and other wireless media

Further, terms like “user equipment,” “user device,” “mobile device,”“mobile,” station,” “access terminal,” “terminal,” “handset,” andsimilar terminology, generally refer to a wireless device utilized by asubscriber or user of a wireless communication network or service toreceive or convey data, control, voice, video, sound, gaming, orsubstantially any data-stream or signaling-stream. The foregoing termsare utilized interchangeably in the subject specification and relateddrawings. Likewise, the terms “access point,” “node B,” “base station,”“evolved Node B,” “cell,” “cell site,” and the like, can be utilizedinterchangeably in the subject application, and refer to a wirelessnetwork component or appliance that serves and receives data, control,voice, video, sound, gaming, or substantially any data-stream orsignaling-stream from a set of subscriber stations. Data and signalingstreams can be packetized or frame-based flows. It is noted that in thesubject specification and drawings, context or explicit distinctionprovides differentiation with respect to access points or base stationsthat serve and receive data from a mobile device in an outdoorenvironment, and access points or base stations that operate in aconfined, primarily indoor environment overlaid in an outdoor coveragearea. Data and signaling streams can be packetized or frame-based flows.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,” andthe like are employed interchangeably throughout the subjectspecification, unless context warrants particular distinction(s) amongthe terms. It should be appreciated that such terms can refer to humanentities, associated devices, or automated components supported throughartificial intelligence (e.g., a capacity to make inference based oncomplex mathematical formalisms) which can provide simulated vision,sound recognition and so forth. In addition, the terms “wirelessnetwork” and “network” are used interchangeable in the subjectapplication, when context wherein the term is utilized warrantsdistinction for clarity purposes such distinction is made explicit.

Moreover, the word “exemplary” is used herein to mean serving as anexample, instance, or illustration. Any aspect or design describedherein as “exemplary” is not necessarily to be construed as preferred oradvantageous over other aspects or designs. Rather, use of the wordexemplary is intended to present concepts in a concrete fashion. As usedin this application, the term “or” is intended to mean an inclusive “or”rather than an exclusive “or”. That is, unless specified otherwise, orclear from context, “X employs A or B” is intended to mean any of thenatural inclusive permutations. That is, if X employs A; X employs B; orX employs both A and B, then “X employs A or B” is satisfied under anyof the foregoing instances. In addition, the articles “a” and “an” asused in this application and the appended claims should generally beconstrued to mean “one or more” unless specified otherwise or clear fromcontext to be directed to a singular form.

In addition, while a particular feature may have been disclosed withrespect to only one of several implementations, such feature may becombined with one or more other features of the other implementations asmay be desired and advantageous for any given or particular application.Furthermore, to the extent that the terms “includes” and “including” andvariants thereof are used in either the detailed description or theclaims, these terms are intended to be inclusive in a manner similar tothe term “comprising.”

What is claimed is:
 1. A device, comprising: a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: receivingconstraint data indicative of a constraint on a physical location of aprocessing device that is employed to execute a network function in avirtual environment; performing a selection procedure that selects theprocessing device that is to execute the network function, the selectionprocedure comprising: determining a target location that satisfies theconstraint data; and matching the target location to referent identifierdata that is assigned to the processing device, the referent identifierdata comprising: device data that identifies the processing devicerelative to other devices other than the processing device and referencedata that identifies the other devices.
 2. The device of claim 1,wherein the constraint data is determined to be satisfied in response tothe network function being executed within a specified jurisdiction. 3.The device of claim 1, wherein the constraint data is determined to besatisfied in response to the network function being executed within aspecified geographical space.
 4. The device of claim 1, wherein theconstraint data is determined to be satisfied in response to the networkfunction being executed at a first location that is within a defineddistance from a second location.
 5. The device of claim 4, wherein thedefined distance is determined based on a latency calculation indicativeof a latency that results from communication between the first locationand the second location.
 6. The device of claim 1, wherein theoperations further comprise instructing the processing device to executethe network function.
 7. The device of claim 1, wherein the operationsfurther comprise instructing the processing device to associate thenetwork function with the referent identifier data, resulting in arecord of the physical location of the processing device that executesthe network function.
 8. The device of claim 1, wherein the processingdevice is one of a group of processing devices situated on a floor of abuilding, and wherein the referent identifier data identifies the floorand the building.
 9. The device of claim 1, wherein the processingdevice is one of a group of processing devices situated in a shelf of adevice bay, and wherein the referent identifier data identifies theshelf and the device bay.
 10. The device of claim 1, wherein the devicedata and the reference data are non-unique identifiers that, whencombined, represent a unique identifier.
 11. The device of claim 1,wherein the operations further comprise, in response to a determinationthat the processing device has spare computing capacity, generatingstatus data comprising the referent identifier data and an indicatorthat indicates the processing device has spare computing capacity. 12.The device of claim 1, wherein the operations further comprise, inresponse to a determination that the processing device is to beserviced, generating status data comprising the referent identifier dataand an indicator that indicates the processing device is to be serviced.13. A machine-readable storage medium, comprising executableinstructions that, when executed by a processor, facilitate performanceof operations, comprising, comprising: receiving constraint dataindicative of a constraint on a physical location of a processing devicethat is employed to execute a network function in a virtual environment;performing a selection procedure that selects the processing device thatis to execute the network function, the selection procedure comprising:determining a target location that satisfies the constraint data;matching the target location to referent identifier data that isassigned to the processing device, the referent identifier datacomprising: device data that identifies the processing device relativeto other devices other than the processing device and reference datathat identifies the other devices; and instructing the processing deviceto execute the network function.
 14. The machine-readable storage mediumof claim 13, wherein the device data and the reference data arenon-unique identifiers that, when combined, represent a uniqueidentifier.
 15. The machine-readable storage medium of claim 13, whereinthe constraint data is determined to be satisfied in response to thenetwork function being executed within a specified geographical spacethat is specified by the constraint.
 16. The machine-readable storagemedium of claim 13, wherein the constraint data is determined to besatisfied in response to the network function being executed at a firstlocation that is within a defined distance from a second location.
 17. Amethod, comprising: receiving, by a device comprising a processor,constraint data indicative of a constraint on a physical location of aprocessing device that is employed to execute a network function in avirtual environment; performing, by the device, a selection procedurethat selects the processing device that is to execute the networkfunction, the selection procedure comprising: determining, by thedevice, a target location that satisfies the constraint data; matching,by the device, the target location to referent identifier data that isassigned to the processing device, the referent identifier datacomprising: device data that identifies the processing device relativeto other devices other than the processing device and reference datathat identifies the other devices; and instructing, by the device, theprocessing device to execute the network function.
 18. The method ofclaim 17, further comprising, instructing, by the device, the processingdevice to associate the network function with the referent identifierdata, resulting in a record of the physical location of the processingdevice that executes the network function.
 19. The method of claim 17,further comprising, in response to a determination that the processingdevice has spare computing capacity, generating, by the device, statusdata comprising the referent identifier data and an indicator thatindicates the processing device has spare computing capacity.
 20. Themethod of claim 17, further comprising, in response to a determinationthat the processing device is to be serviced, generating, by the device,status data comprising the referent identifier data and an indicatorthat indicates the processing device is to be serviced.